increase version number#210
Conversation
WalkthroughThe Docker image tag used in the GitHub Actions build workflow is updated from version 3.2.0 to 3.3.0. This affects the version identifier for Docker images pushed to Docker Hub during the develop branch builds. Changes
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| build-gradle-project: | ||
| env: | ||
| IMAGE_TAG: 3.2.0 | ||
| IMAGE_TAG: 3.3.0 |
There was a problem hiding this comment.
Line 9 introduces a build/push tag mismatch that can break develop pushes.
IMAGE_TAG is now 3.3.0, but build.gradle is still version = '3.2.0' (Context snippet: build.gradle:15-16), and your Gradle docker task tags from project.version on develop (Context snippet: build.gradle:78-88).
Result: workflow may try to push kingstonduo/pegasus-data:3.3.0 even though only :3.2.0 was built.
Suggested fix
# Option A: keep versions aligned immediately
- IMAGE_TAG: 3.3.0
+ IMAGE_TAG: 3.2.0# Option B (preferred): single source of truth
# bump build.gradle to 3.3.0 in same PR, or compute IMAGE_TAG from Gradle project.version before push📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| IMAGE_TAG: 3.3.0 | |
| IMAGE_TAG: 3.2.0 |
2 participants
Summary by CodeRabbit
Release Notes